Objective

• Follows Move MaterialProperties from bevy_pbr to bevy_material bevyengine/bevy#21543
• bevy_gltf shouldn't require knowledge of HOW its rendered

Solution

• Added ShortStandardMaterial to bevy_material , this is a subset of fields in bevy_pbr::StandardMaterial
• Added MarkerMeshMaterial3d to bevy_material , this has a Handle to the ShortStandardMaterial
• Added a system swap_marker_mesh_material_3d to bevy_pbr that:
  • queries for MarkerMeshMaterial3d
  • creates a StandardMaterial from the ShortStandardMaterial
  • removes the MarkerMeshMaterial3d
  • adds a MeshMaterial3d with the new StandardMaterial

Please bikeshed ShortStandardMaterial and MarkerMeshMaterial3d

Above removes the direct dependency, but adds an indirect one.

Alternative

I could move ShortStandardMaterial to bevy_gltf (rename it GltfMaterial ) , and then have a new crate bevy_gltf_render that depends on bevy_pbr , and somehow split load_node to add the MeshMaterial3d , but that would be a much larger change. I think this is simpler

See #6

Testing

• cargo run --example load_gltf